chore(release): bump to 0.0.2#13
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Bump
0.0.1->0.0.2inpackage.json+package-lock.json(npm install sync; also picks up the stalelicense: MITfield in the lock root that #12 did not touch).Why
The workflow_dispatch publish of
0.0.1failed with npm E400 "Cannot publish over previously published version":0.0.1was published and then unpublished on 2026-07-05, and npm permanently bans reusing an unpublished version number. A fresh version is required.Publish on merge
The squash subject
chore(release): bump to 0.0.2matches the publish.yml release gate (^chore\(release\)), and the push touchespackage.json, so merge auto-publishes0.0.2.Note: npm may also enforce a 24h cooldown after a full unpublish (until ~2026-07-06T22:37Z); if merged before then, publish may fail with E403 and needs a re-run (workflow_dispatch) after the window.